home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Performance Co-Pilot 1.3
/
SGI Performance Co-Pilot 1.3.iso
/
dist
/
pcp.idb
/
usr
/
share
/
catman
/
u_man
/
cat1
/
pmtime.z
/
pmtime
Wrap
Text File
|
1997-04-03
|
5KB
|
67 lines
PPPPMMMMTTTTIIIIMMMMEEEE((((1111)))) PPPPMMMMTTTTIIIIMMMMEEEE((((1111))))
NNNNAAAAMMMMEEEE
ppppmmmmttttiiiimmmmeeee - Performance Co-Pilot time control server
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
////uuuussssrrrr////ppppccccpppp////bbbbiiiinnnn////ppppmmmmttttiiiimmmmeeee [----aaaa] [----hhhh] ----pppp _p_o_r_t_n_a_m_e
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
ppppmmmmttttiiiimmmmeeee provides a graphical user interface for PCP applications requiring
time control. ppppmmmmttttiiiimmmmeeee is not normally invoked directly by users. Rather,
it is run by calling the Performance Metrics Application Programming
Interface (PMAPI) function ppppmmmmTTTTiiiimmmmeeeeCCCCoooonnnnnnnneeeecccctttt(3).
The ----pppp argument is required. When ppppmmmmttttiiiimmmmeeee starts, it creates _p_o_r_t_n_a_m_e in
the file system. This is a Unix domain socket serving as the control
port that ppppmmmmttttiiiimmmmeeee will accept new connections on.
When starting, ppppmmmmttttiiiimmmmeeee creates and initializes an instance of the
VVVVkkkkPPPPCCCCPPPPaaaarrrrcccchhhhiiiivvvveeeeTTTTiiiimmmmeeee(3) ViewKit dialog (when run with ----aaaa) or an instance of
the VVVVkkkkPPPPCCCCPPPPlllliiiivvvveeeeTTTTiiiimmmmeeee(3) dialog (when run with the ----hhhh option). In live mode,
ppppmmmmttttiiiimmmmeeee will also invoke the ssssttttaaaarrrrtttt(((()))) method of VVVVkkkkPPPPCCCCPPPPlllliiiivvvveeeeTTTTiiiimmmmeeee(3). The
dialog will be initially managed (visible) only if the client requested
it, as described in ppppmmmmTTTTiiiimmmmeeeeCCCCoooonnnnnnnneeeecccctttt(3).
ppppmmmmttttiiiimmmmeeee will then enter it's main loop, accepting new connections and
sending time control IPC messages to it's client(s). These messages are
described in detail in ppppmmmmttttiiiimmmmeeee(3).
When the number of connected clients reaches zero, ppppmmmmttttiiiimmmmeeee will remove the
control socket and exit. Clients disconnect either by calling
ppppmmmmTTTTiiiimmmmeeeeDDDDiiiissssccccoooonnnnnnnneeeecccctttt(3) or simply exiting (implicitly closing the socket
connections).
The arguments to ppppmmmmttttiiiimmmmeeee are as follows;
----aaaa Use archive mode. This instructs ppppmmmmttttiiiimmmmeeee to create an instance of
the VVVVkkkkPPPPCCCCPPPPaaaarrrrcccchhhhiiiivvvveeeeTTTTiiiimmmmeeee(3) class, allowing full VCR control. This
argument is mutually exclusive with ----hhhh.
----hhhh Use live (host) mode. This instructs ppppmmmmttttiiiimmmmeeee to create an instance
of the VVVVkkkkPPPPCCCCPPPPlllliiiivvvveeeeTTTTiiiimmmmeeee(3) class. This argument is mutually exclusive
with ----aaaa.
----pppp Specifies the path to the control port, as described above. If
_p_o_r_t_n_a_m_e already exists, ppppmmmmttttiiiimmmmeeee will display an error message and
exit. When ppppmmmmttttiiiimmmmeeee exits, it removes _p_o_r_t_n_a_m_e.
SSSSEEEEEEEE AAAALLLLSSSSOOOO
PPPPMMMMAAAAPPPPIIII(3), ppppmmmmttttiiiimmmmeeee(3), VVVVkkkkIIIInnnnppppuuuutttt(3x), VVVVkkkkPPPPCCCCPPPPaaaarrrrcccchhhhiiiivvvveeeeTTTTiiiimmmmeeee(3x),
VVVVkkkkPPPPCCCCPPPPlllliiiivvvveeeeTTTTiiiimmmmeeee(3x), VVVVkkkkPPPPCCCCPPPPttttiiiimmmmeeeerrrr(3x), XXXXttttMMMMaaaaiiiinnnnLLLLoooooooopppp(3x), XXXXttttAAAAppppppppAAAAddddddddIIIInnnnppppuuuutttt(3x)
PPPPaaaaggggeeee 1111